| From: | Ben Hutchings |
| Date: | 14 Aug 99 at 01:49:28 |
| Subject: | Re: Re: Accessing Broken SCSI |
From: Ben Hutchings <womble@zzumbouk.demon.co.uk>
On Fri, Aug 13, 1999 at 10:13:11AM -0500, Jack York wrote:
> From: Jack York <jyork@voyager.net>
>
> Hello Ben
>
> On 11-Aug-99, Ben Hutchings wrote:
> > From: Ben Hutchings <womble@zzumbouk.demon.co.uk>
> >
> > On Wed, Aug 11, 1999 at 02:10:00PM -0500, Jack York wrote:
> >> From: Jack York <jyork@voyager.net>
> >>
> >> Hello,
> >>
> >> I am trying to recover some data from a scsi drive on which the RDB
> >> is lost. I have never tried doing anything with the SCSI device
> >> so I may be way off here, but my thought was to take the sample
> >> code below (from the RKM Scsi_direct example) and change it to a
> >> a SCSIF_READ command.
> > <snip>
> >
> > Why not use a plain CMD_READ (or TD_READ64 if the drive is bigger
> > than 4 GB)?
>
> As I said I never tried anything with the SCSI device so I am just
> trying to convert some code to my purposes. CMD_READ may well be
> easier but without an example it still isn't clear.
See the documentation of trackdisk.device - trackdisk.doc, the RKRM:
Devices section on it, and example code. SCSI device drivers support
virtually all trackdisk functionality (there are a few commands that
are documented as specific to trackdisk.device).